Method and apparatus for controlling input to a mobile computing device located inside a vehicle

ABSTRACT

A wireless transmission system is provided that includes a transmission apparatus that transmits a wireless signal indicative of a vehicle parameter. The system includes a mobile computing device having an input device for accepting user input and a wireless transceiver configured to receive the wireless signal. The mobile computing device includes a processor that communicates with the wireless transceiver and the input device. The processor is configured to run an application that disables the input device if the vehicle parameter exceeds a threshold. The processor is further configured to detect if the application is disabled.

TECHNICAL FIELD

The present invention relates to a method and system used to control amobile computing device to prevent input to the device when the deviceis inside a vehicle which is in motion.

BACKGROUND

Modern computing devices, such as cellular telephones, PDAs and laptopcomputers provide a keyboard functionality, implemented via hardware orsoftware, for the purposes of inputting textual data by an operator.Utilizing this keyboard input functionality while operating a motorvehicle has become a significant safety hazard in recent years due tothe increasing prevalence of such devices. The act of doing so poses arisk of injury or death to the operator, the passengers of theoperator's vehicle, other vehicles and pedestrians, due to the degree ofattention required to operate keyboard input devices. Thus, it isdesirable to selectively enable and disable keyboard input functionalityon mobile devices in the possession of the operator of a motor vehiclewhile said vehicle is in motion.

Various devices or applications have been proposed to address thetexting while driving problem. Of these, many deal with jamming cellphone signals which have the drawback that all cell phones in a vehicleare thus disabled. Further, such jamming does not prevent other use ofthe mobile devices. Other systems relate to RF signals which require useof circuitry not normally employed in cellphones. Hence, a system andmethod is needed to economically provide for inhibiting texting andother uses of cellphones and other mobile computing devices whiledriving a vehicle.

Many of the conventional devices or applications used to address thetexting while driving problem can be turned off or otherwisecircumvented. Information regarding whether a user turned off orcircumvented the device or application and/or the status of the devicecould be important when the user is involved in a car accident. Forexample, whether or not the user was using the device at the time of theaccident may affect liability. Indeed, it may show whether textingduring driving was or was not at least partially the cause of theaccident, thus eliminating other factors, such as, for example, weatherconditions or another driver. Hence, a system and method is needed toprovide information concerning the status of a device and/or whether ornot a user disabled an application used to address the texting whiledriving problem.

SUMMARY

A wireless transmission system provided in accordance with the presentdisclosure. The system is configured for use in a vehicle having anon-board diagnostic (OBD) system that provides vehicle speed data andengine operation status data, for example. A transmission apparatus isconfigured to interface with the OBD system. The transmission apparatusis configured to transmit a wireless signal, such as, for example, awireless signal specified by Bluetooth criteria. In some embodiments,the wireless signal includes vehicle speed data. The system includes amobile computing device having an input device and a wirelesstransceiver configured to receive the wireless signal. In someembodiments, the mobile computing device includes a processor that runsan application that disables the input device if the vehicle speed is ator above a threshold value.

In some embodiments, the transceiver receives the wireless signal anddetermines a signal level or strength of the wireless signal. Theapplication determines if the mobile computing device is within acertain area, such as, for example, a driver's seating area, based uponthe strength of the wireless signal, and disables the input device if(a) the vehicle speed is at or above a threshold value and (b) themobile computing device is within the driver's seating area.

In some embodiments, the mobile computing device includes an inputcontrol configuration for effecting the following operations: (a)bonding with the transmission device; b) reading a received signal levelfrom the wireless transceiver; (c) comparing the received signal levelwith a signal strength level (SLL) threshold value; (d) determining avehicle speed based on data from the OBD system and/or the mobilecomputing device; (e) comparing the vehicle speed with a vehicle speedthreshold; and (f) disabling the input device when the received signallevel is at or above the SLL threshold value and the vehicle speed is ator above the vehicle speed threshold. In some embodiments, the inputcontrol configuration further effects repeating operations (a) through(f); and re-enabling the input device when the received signal level isbelow the SLL threshold value, or the vehicle speed is below the vehiclespeed threshold.

In some embodiments, the processor is configured to detect if a userdisables and/or circumvents the application that disables the inputdevice if the vehicle speed is at or above a threshold value and/or themobile computing device is with a driver's seating area. In someembodiments, the processor creates a log of each time the application isdisabled. In some embodiments, the log includes dates and times when theapplication is disabled. In some embodiments, the processor isconfigured to send an alert if the application is disabled.

In some embodiments, the transmission apparatus is in communication withthe OBD system of the vehicle and the OBD system is configured to detectthe vehicle's engine status, speed of travel and GPS location. Theapplication is configured to be paired to the OBD system and theapplication creates a log that includes the vehicle's engine status,speed of travel and GPS location when the input device is disabled bythe application. In some embodiments, the log includes dates and timeswhen the input device is disabled by the application. In someembodiments, the OBD system is configured to store accident data that isincluded in the log. That is, the log includes data that indicateswhether the input device was disabled by the application at the time anaccident occurred.

In some embodiments, a method is provided in accordance with the presentdisclosure. The method includes disabling the input device using theapplication if a vehicle parameter, such as, for example, the speed ofthe vehicle, exceeds a threshold. In some embodiments, the processordetects if the application is disabled. In some embodiments, the methodincludes sending an alert each time the application is disabled. In someembodiments, the method includes creating a log of when the applicationis disabled.

In some embodiments, the method includes pairing the application withthe OBD system and the OBD system is configured to detect the vehicle'sengine status, speed of travel and GPS location. The application createsa record of various metrics, such as, for example, engine status (e.g.,running or not), speed of travel (vehicle provided and GPS) and keyboardstatus (enabled or not). In some embodiments, the method includescreating a log using data from the record. The log may establish whereand when the keyboard is disabled. In some embodiments, the methodincludes sending the log to a third party, such as, for example,previously established owner contact and/or insurance company.

In some embodiments, the method includes comparing the log to recordeddata, such as, for example, “black box” accident data. In someembodiments, the processor compares the log to the recorded data. Insome embodiments, the recorded data is compiled or otherwise stored bythe OBD system. In some embodiments, comparing the log to the recordeddata establishes a state of the mobile device at the time of an accidentfor the purpose of establishing liability, for example. This may help indetermining whether or not the mobile device was in use at the time theaccident occurred.

In some embodiments, the method includes managing the log. In someembodiments, the log is managed by an end user. In some embodiments, themethod includes transmitting the log to a third party. In someembodiments, the third party is an entity responsible for managing anumber of vehicles and drivers, such as, for example, a delivery serviceor other service provider. In some embodiments, the third party is aninsurance company. In some embodiments, the third party is able to viewor delete the log, but cannot modify the log.

The above and other objects, features and advantages of the presentinvention will become apparent from the following description read inconjunction with the accompanying drawings, in which like referencenumerals designate the same elements. The present invention isconsidered to include all functional combinations of the above describedfeatures and corresponding descriptions contained herein, and allcombinations of further features described herein, and is not limited tothe particular structural embodiments shown in the figures as examples.The scope and spirit of the present invention is considered to includemodifications as may be made by those skilled in the art having thebenefit of the present disclosure which substitute, for elementspresented in the claims, devices or structures upon which the claimlanguage reads or which are equivalent thereto, and which producesubstantially the same results associated with those correspondingexamples identified in this disclosure for purposes of the operation ofthis invention. Additionally, the scope and spirit of the presentinvention is intended to be defined by the scope of the claim languageitself and equivalents thereto without incorporation of structural orfunctional limitations discussed in the specification which are notreferred to in the claim language itself.

Additional features and advantages of various embodiments will be setforth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of variousembodiments. The objectives and other advantages of various embodimentswill be realized and attained by means of the elements and combinationsparticularly pointed out in the description and appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In part, other aspects, features, benefits and advantages of theembodiments will be apparent with regard to the following description,appended claims and accompanying drawings where:

FIG. 1 is a block diagram of a system of the present disclosure;

FIG. 2 is an illustration of an installation of the system shown in FIG.1;

FIG. 3a is a flowchart of operation of an application program inaccordance with the present disclosure;

FIG. 3b is a flowchart of operation of a portion of the applicationprogram flowchart of FIG. 3 a;

FIG. 3c is a flowchart of operation of a first embodiment of a speeddetermining portion of the application program flowchart of FIG. 3 a;

FIG. 3d is a flowchart of operation of a second embodiment of a speeddetermining portion of the application program flowchart of FIG. 3 a;

FIG. 3e is a flowchart of operation of a third embodiment of a speeddetermining portion of the application program flowchart of FIG. 3 a;

FIG. 3f is a flowchart of operation of a fourth embodiment of a speeddetermining portion of the application program flowchart of FIG. 3 a;

FIG. 4 is a flowchart of operation of a transmission apparatus of thepresent disclosure;

FIG. 5 is a block diagram of another embodiment of a transmissionapparatus of the present disclosure;

FIG. 6 is a flowchart of operation of one embodiment of an applicationprogram in accordance with the present disclosure;

FIG. 6a is a flowchart of operation of one embodiment of an applicationprogram in accordance with the present disclosure;

FIG. 7 is a flowchart of operation of one embodiment of an applicationprogram in accordance with the present disclosure; and

FIG. 7a is a flowchart of operation of one embodiment of an applicationprogram in accordance with the present disclosure.

It is to be understood that the figures are not drawn to scale. Further,the relation between objects in a figure may not be to scale, and may infact have a reverse relationship as to size. The figures are intended tobring understanding and clarity to the structure of each object shown,and thus, some features may be exaggerated in order to illustrate aspecific feature of a structure.

DETAILED DESCRIPTION

For the purposes of this specification and appended claims, unlessotherwise indicated, all numbers expressing quantities of ingredients,percentages or proportions of materials, reaction conditions, and othernumerical values used in the specification and claims, are to beunderstood as being modified in all instances by the term “about.”Accordingly, unless indicated to the contrary, the numerical parametersset forth in the following specification and attached claims areapproximations that may vary depending upon the desired propertiessought to be obtained by the embodiments of the present disclosure. Atthe very least, and not as an attempt to limit the application of thedoctrine of equivalents to the scope of the claims, each numericalparameter should at least be construed in light of the number ofreported significant digits and by applying ordinary roundingtechniques.

Notwithstanding that the numerical ranges and parameters setting forththe broad scope of the invention are approximations, the numericalvalues set forth in the specific examples are reported as precisely aspossible. Any numerical value, however, inherently contains certainerrors necessarily resulting from the standard deviation found in theirrespective testing measurements. Moreover, all ranges disclosed hereinare to be understood to encompass any and all subranges subsumedtherein. For example, a range of “1 to 10” includes any and allsubranges between (and including) the minimum value of 1 and the maximumvalue of 10, that is, any and all subranges having a minimum value ofequal to or greater than 1 and a maximum value of equal to or less than10, e.g., 5.5 to 10.

It is noted that, as used in this specification and the appended claims,the singular forms “a,” “an,” and “the,” include plural referents unlessexpressly and unequivocally limited to one referent. Thus, for example,reference to “a drug depot” includes one, two, three or more drugdepots.

It is to be further understood that all disclosure of immediateconnections between elements of the present disclosure are intended topositively disclose direct connections without intervening elements, butare not intended to exclude incorporation of intervening elements unlessspecifically related in claim language. Similarly, it is to beunderstood that with regard to methods and flowcharts herein, adisclosure of operations directly following one another, or a disclosureof steps wherein a first step directly follows a second step, isintended to positively disclose direct sequential following withoutintervening operations, but is not intended to exclude interveningoperations unless explicitly related in claim language.

It is also to be further understood that the doctrine of claimdifferentiation is to be applied between independent claims and theirdependents and is not intended to be applied across independent claims.For example, term A in a first independent claims may be interpreted tohave the same scope as term B in a second independent claim, while ifterm A is in a first independent claim and term B further defines term Ain claim dependent from the first independent claim, then term A musthave a broader scope than term B. In other words, phrases that differfrom one independent claim to another independent claim may beinterpreted to have equal scope and read on common structure yet presentthe structure using different terminology in order to account fordiffering interpretation of phrase language.

Reference will now be made in detail to various embodiments of thepresent disclosure, examples of which are illustrated in theaccompanying drawings. While the embodiments of the present disclosurewill be described in conjunction with the illustrated embodiments, itwill be understood that they are not intended to limit the invention tothose embodiments. On the contrary, the invention is intended to coverall alternatives, modifications, and equivalents, which may be includedwithin the invention as defined by the appended claims.

The headings below are not meant to limit the disclosure in any way;embodiments under any one heading may be used in conjunction withembodiments under any other heading.

The foregoing summary broadly details some embodiments of the presentdisclosure. In another embodiment of the present disclosure the wirelesstransmission system optionally provides the transmission apparatusconfigured to transmit OBD system speed data. Furthermore the inputcontrol configuration effects using the OBD system speed data as thevehicle speed if the GPS data is not available.

In a further embodiment of the present disclosure, the wirelesstransmission system optionally includes the transmission apparatusdetermining from the OBD system whether an engine of the vehicle isrunning and transmits the wireless signal in response to determiningthat the engine is running.

In a still further embodiment of the present disclosure, the wirelesstransmission system includes the input control configuration beingeffected by software loaded into a memory of the mobile computingdevice.

In a yet further embodiment of the present disclosure, the wirelesstransmission system optionally has the input control configurationeffected by firmware loaded into a memory of the mobile computingdevice.

In a still further aspect of the present disclosure, the input device isoptionally a keyboard device.

In yet a further embodiment of the present disclosure, the wirelesstransmission system optionally includes the transmission apparatus andthe transceiver of the mobile computing device effecting automaticbonding.

In another embodiment of the present disclosure, the wirelesstransmission system optionally provides the transmission apparatusconfigured to transmit OBD system speed data. Furthermore the inputcontrol configuration effects using the OBD system speed data as thevehicle speed if the GPS data is not available.

In a further embodiment of the present disclosure the wirelesstransmission system optionally includes the transmission apparatusdetermining from the OBD system whether an engine of the vehicle isrunning and transmits the wireless signal in response to determiningthat the engine is running.

In an embodiment of the present disclosure, the wireless transmissionsystem includes the input control configuration being effected bysoftware loaded into a memory of the mobile computing device.

In a yet further embodiment of the present disclosure, the wirelesstransmission system optionally has the input control configurationeffected by firmware loaded into a memory of the mobile computingdevice.

In a still further aspect of the present disclosure, the input device isoptionally a keyboard device.

In yet a further embodiment of the present disclosure, the wirelesstransmission system optionally includes the transmission apparatus andthe transceiver of the mobile computing device effecting automaticbonding.

In some embodiments, the system creates a log if a user attempts todisable or otherwise circumvent the application when the applicationdisables the input device. In some embodiments, the log is created inresponse to a request that is sent from the mobile computing device to aserver. In some embodiments, the log is created by the processor. Insome embodiments, the processor sends an alert to a previouslyestablished owner contact to notify the owner contact that theapplication has been disabled and/or circumvented while the applicationdisabled the input device.

In some embodiments, the application can be paired with the OBD systemto allow the application to record various data acquired by the OBDsystem. In some embodiments, the data acquired by the OBD systemincludes engine status of the vehicle, speed of the vehicle and locationof the vehicle. The application creates a log when the input device isdisabled, the log including at least some of the data acquired by theOBD system such that the log includes information concerning the stateof the vehicle when the input device was disabled. In some embodiments,the log includes the date and time that the input device was disabled.In some embodiments, the data acquired by the OBD system includes “blackbox” accident data that is included in the log. In some embodiments, thelog is managed by an end user, such as, for example, an owner of themobile computing device. In some embodiments, the application isconfigured to send the log to a third party and the log is managed bythe third party. In some embodiments, the log may be viewed and/ordeleted by the end user and/or third party. In some embodiments, the logcannot be modified by the end user or third party.

Mobile Computing Device (MCD), as used herein and throughout thisdisclosure, refers to any electronic device equipped with at least oneof the following: a processor, memory, display, operating system andinput function. Examples of such devices are portable “laptop”computers, tablets, personal digital assistants (PDA), “smart” mobiletelephones (smartphones), or other types of devices which may yet bedeveloped which provide at least some of the functions of the aforesaidexemplary devices.

Input Function, as used herein and throughout this disclosure, refers toany hardware or software arrangement of input buttons whose primaryfunction is to trigger data input to a mobile computing device whenmanipulated by a human, either by direct tactile interaction or via theuse of a pen, stylus or other implement. Typically the input function isthe keyboard on a smartphone which may include a physical keyboard or asimulated keyboard on a touch-screen.

Apparatus, as used herein and throughout this disclosure, refers to anydevice to interface the OBD system to gather speed data and to interfaceto a wireless transmitter for transmission of speed data to one or moremobile computing devices.

Application Program, as used herein and throughout this disclosure,refers to a software or firmware program that operates within the mobilecomputing device which retrieves speed data, retrieves measured signalstrength, uses method to determine owner of mobile computing device, anddisables input function of mobile computing device if the mobilecomputing device is held by or located near to the driver of the motorvehicle

Signal Strength Level Threshold, as used herein and throughout thisdisclosure, refers to a pre-determined number or set of numbers that isused to compare against a measured signal strength for determining thelocation a mobile computing device. The signal strength level thresholdis determined by measurements recorded within a motor vehicle,calculated using simulation tools that model the inside of a motorvehicle or some combination of the two.

Speed Threshold, as used herein and throughout this disclosure, refersto a pre-determined number that is used to compare against a motorvehicle speed to determine if operation of a mobile computing device issafe to use.

Bluetooth® Low Energy (BLE), Bluetooth® LE, Bluetooth® Smart, as usedherein and throughout this disclosure, refers to a specific wirelesspersonal area network technology designed and marketed by the BluetoothSpecial Interest Group. It differs in nature and application fromconventional Bluetooth® implementations. Bluetooth® Low Energy (BLE),Bluetooth® LE and Bluetooth® Smart are used interchangeably.

Motor Vehicle, as used herein and throughout this disclosure, includes acar, truck, bus, motorcycle or other motorized vehicle, and may beequipped with an OBD port.

Operator Control Area, as used herein and throughout this disclosure, isthe physical area where the driver is positioned during operation of themotor vehicle and includes a driver's seat, steering wheel, centerconsole, instrument cluster, ashtray and sun visor.

Referring to FIG. 1, a vehicle 100 has an On-Board diagnostics system(OBD) 102 installed therein which monitors various sensors in thevehicle including a sensor for the engine running state and a sensorreporting a speed of the vehicle 100. The OBD 102 provides a DiagnosticLink Connector (DLC) 161 which is a 16 pin connector for interfacingwith test instrumentation. The OBD 102 was initially developed toprovide diagnostics for maintenance of the vehicle 100, in particular,the emissions control devices of the vehicle 100. Various governmentregulations are presently implemented to require that vehicles have anOBD 102 which conforms to the OBD-II standard which requires variousemission parameters to be communicated but which also allow manyoptional parameters to also be communicated. Automobile manufactures nowuse this system to communicate information regarding many aspects ofvehicle operation, including the speed of the vehicle and whether theengine is running. For the purpose of the present disclosure, it is notrequired that the OBD 102 conform to any specific standard except thatthe OBD provide functioning in accordance with the specific functionsrelated in this disclosure for practice of embodiments of the system andmethod described herein.

The system of the present disclosure includes a transmission apparatus130 which optionally includes a controller 104 and a wirelesstransceiver 105. The transmission apparatus 130 is designed to emit awireless link signal 170 that will be measured by MCD 110. Thecontroller 104 can be of any type having memory and the functionality toeffect operations detailed herein. Optionally, the controller 104 is asmall low-power microcontroller such as, for example and not intended asa limitation, an Atmel tinyAVR series, Atmel SAM3U series or similar,which are optionally configured to interface with the wirelesstransceiver 105 to produce the wireless link signal 170 that can bemeasured by the MCD 110. Wireless transceivers may be of any typecompatible with the MCD 110 including technologies based on Bluetooth®,Bluetooth® Smart, or a WiFi, type transmission for example and notlimitation. For example, wireless transceiver 105 may be designed usingNordic nRF51422 Bluetooth® Smart transceiver. Alternatively, thecontroller 104 and the wireless transceiver 105 are combined into asingle integrated unit. For example, many wireless transceivers includean embedded microcontroller as part of the integrated circuit packagesuch as Texas Instrument CC2640. It is to be understood for the purposeof this disclosure that functions the controller 104 and the wirelesstransceiver 105 may be integrated together or distributed amongstvarious types of electronic components. For example, whilemicrocontrollers provide both a CPU and memory for storing programmingdirected to a specific computing application to provide a cost effectivesolution, similar functionality may be obtained by providing independentCPU and memory components.

The system and method of the present disclosure further includes the MCD110 configured to provide the functionality described herein. The MCD110 includes a wireless transceiver 106 of a similar type to wirelesstransceiver 105 that allows the wireless link signal 170 to beestablished between the transmission apparatus 130 and the MCD 110. Thewireless link signal 170 may be designed as a broadcast link wherecommunications occur from the transmission apparatus 130 to the MCD 110.The wireless link signal 170 may be designed as a two-way link wherecommunications occurs from the transmission apparatus 130 to the MCD 110and from the MCD 110 to the transmission apparatus 130. In an embodimentof the present disclosure, the transceiver 105 of the transmissionapparatus 130 and the transceiver 106 of the MCD 110 are Bluetooth®Smart compliant transceivers configured to automatically pair when thetwo transceivers are in close proximity. Alternatively, other Bluetooth®compliant systems may be used, or future developed wireless datatransmission systems may be optionally used within the scope and spiritof the present disclosure.

The MCD 110 includes memory and an application program 111, oftenreferred to as an “app” in present day parlance, designed to receive thesignal level measured at the transceiver 106 that was transmitted fromthe transceiver 105. The application program 111 may be installed on theMCD 110 by the user or the application program may be incorporated inthe MCD 110 at the time of manufacture in the form of software. Stillfurther, the application program 111 is optionally incorporated into theMCD 110 in the form of firmware designed into the MCD 110 whenmanufactured. The use of firmware prevents a user from removing theapplication program from the MCD 110. It is further contemplated thatthe application software optionally includes anti-removal code toprevent removal of the software after installation. Such anti-removalcode may either prevent removal outright, or it may invoke apermanently, or semi-permanently disabling feature on the MCD 110, suchas a disabling input device, display, or other features. In such animplementation, the disabling feature may be configured to permitemergency transmissions only such as 911 calls.

The system of the present disclosure addresses the situation whereinboth the transmission apparatus 130 and the MCD 110 are located withinthe motor vehicle 100. The MCD 110 also includes a Global PositioningSystem (GPS) module 112. The GPS module 112 is capable of reporting thespeed at which the MCD is moving, and hence a vehicle speed, to theapplication program 111. Various GPS techniques may be employed todetermine the speed as known to those skilled in the art and are thusnot elaborated upon herein. Additionally, the speed maybe determined bythe application program 111 by taking position readings from the GPSmodule 112 rather than reading a vehicle speed from the GPS module 112.

The application program 111 optionally contains at least two thresholdvariables, namely a speed threshold 114 and an SSL threshold 116. TheSSL threshold 116 is used to determine a physical location of the MCD110 within the motor vehicle 100. The speed threshold 114 is used todecide when the speed of the motor vehicle 100 is too fast for safeoperation of the input function 20 of the MCD 110. The input function 20is any of a physical keyboard, a touchscreen keyboard. The inputfunction 20 is optionally any type of input mechanism as may bedeveloped that requires human attention to operate such as a voicecommand system or a gesturing system. While presently texting by theuser when the user is operating a moving motor vehicle is of greatconcern, it is also envisioned that other types of input, whether forsending communications such as text messages or operating the MCD 110for other purposes, may be discovered to be problematic when operatingthe motor vehicle.

In an embodiment of the present disclosure, the MCD 110 does not requireany hardware modification from the original configuration designed bythe manufacturer to implement the system and method of the presentdisclosure. Most MCDs include a function to disable the keyboard toprevent unintended operation of the device by the user such as when theMCD is in a pocket, purse or briefcase, or to prevent unauthorized useof the MCD. This function is usually built into the operating system ofthe MCD 110 and is accessible by programs running on the MCD 110. Hence,the application program 111 utilizes the disablement function of theoperating system but is not so limited to do so as other programmingtechniques may be employed to implement the disablement feature of thepresent disclosure as may be ascertained by those skilled in the arthaving the benefit of the present disclosure. As noted above, while theapplication program 111 may be loaded by the user, it may also bepre-installed by the manufacturer. The application program 111 may alsobe built-into the MCD 110 in the form of firmware, or hardwired logiccircuitry.

Referring to FIG. 2, a configuration for determining a position of theMCD 110 within the motor vehicle 100 with respect to its proximity to anoperator control area 140 is shown. The transmission apparatus 130 isshown to be located within passenger compartment 150 of the motorvehicle 100. In an embodiment, the transmission apparatus 130 isoptionally located in a nearest proximity to an operator control area140 by virtue of being installed directly into the device link connector161 resulting in the highest measured signal level from the transmissionapparatus 130 at the MCD 110 when the MCD is positioned in operatorcontrol area 140. In accordance with 40 CFR 86.094-17(h)(4), the DLC 161is to be positioned as follows:

-   -   The vehicle connector shall be located in the passenger        compartment in the area bounded by the driver's end of the        instrument panel to 300 mm beyond the vehicle centerline,        attached to the instrument panel, and accessible from the        driver's seat. The preferred location is between the steering        column and the vehicle centerline. The vehicle connector shall        be mounted to facilitate mating and unmating.

The transmission apparatus 130 communicates with the MCD 110 over awireless link signal 170. If the measured signal strength received fromthe transmission apparatus 130 exceeds the SSL threshold 116, the MCD110 is determined to be operated by the driver of the motor vehicle 100and the application program 111 disables the input device 120 on the MCD110 when the motor vehicle 100 is in motion. If the measured signalstrength is below the SSL threshold 116, the MCD 110 is determined to beoperated by a passenger, such as the case shown in FIG. 2, having theMCD 120 located in the rear of the passenger compartment 150. In thiscase, the input device 120 for the MCD 130 will not be disabledregardless of whether the motor vehicle 100 is in motion or not.

In an embodiment, the SSL threshold 116 is optionally a single value towhich to the measured signal strength at the MCD 110 is compared afterbeing transmitted from the transmission apparatus 130. Table 1 shows thevalues for a measured signal strength averaged across three types ofmotor vehicles, namely a sports car, small sedan and SUV. The valuesreported on Table 1 are a function of the distance between thetransmission apparatus 130 and an instrument simulating the measurementfrom the MCD 110. For the measurements in Table 1, the transmissionapparatus 130 was located in operator control area 140 in accordancewith the OBDII standard. Based on the measurements in Table 1, a SSLthreshold 116 of −35 dBm to −40 dBm provides the necessary informationfor determining when the MCD 110 is located in operator control area140. While the aforesaid values are absolute values, it will beunderstood by those skilled in the art of wireless system design, that ameasured signal value will necessarily depend upon the initialtransmission level. Hence, the values provided herein are exemplary innature and may be varied based upon the transmission characteristics ofthe transmission apparatus 130 and the receiving characteristics of theMCD 110. A measured value at or above the SSL threshold 116 wouldindicate the MCD 110 is within the operator control area 140 and ameasured value below the SSL threshold 116 would indicate the MCD 110 isoutside operator control area 140. When the MCD 110 is determined to bewithin operator control area 140, the application program 111 disablesthe input device 120 to the MCD 110 when the motor vehicle 100 is inmotion or determined that the speed of the motor vehicle 100 istraveling at a rate above the speed threshold 114.

TABLE 1 Range Signal (inches) (dBm) Location  6 −10 Driver Seat 12 −15Driver Seat 24 −25 Center console 36 −52 Pass. Seat 48 −70 Pass. Seat 60−80 Rear Seat 72 −91 Rear Seat (SUV)

The values reported in Table 1 are related to the Radio Signal StrengthIndicator (RSSI) that is reported by a variety of commercially availabletransceivers. For example, the Nordic nRF51422 is a Bluetooth® Smarttransceiver which reports RSSI in values of negative dBm with a 1 dBresolution.

Referring to FIG. 3a , an embodiment of a method of determining whetherthe input device 120 of the MCD 110 should be disabled when located inoperator control area 140 is illustrated in a flowchart for operation ofthe application program 111 in the MCD 110. The method starts with thetransmission apparatus 130 executing a wireless link operation 200 toestablish a link, or bond, with the transmission apparatus 130. In anembodiment, the wireless link operation 200 provides an automaticconnection from the transmission apparatus 130 via a Bluetooth® Smartimplementation to the MCD 110. The wireless link operation 200 need notbe a Bluetooth Smart connection and can be any connection where thetransmission apparatus 130 is transmitting a wireless signal that can bemeasured at the MCD 110.

Once the link is established, the MCD 110 executes a signal strengthmeasuring operation 202 which measures the received signal strength ofthe link established. A signal determination operation 204 is nextexecuted to whether or not the signal strength is above a pre-determinedSSL threshold 116 set to coincide with the MCD 110 being located inoperator control area 140. If the measured signal strength is below theSSL threshold 116, the method proceeds to a re-enablement operation 211which determines if the input device 120 is presently disabled andre-enables the input device 120 if it has been disabled. The method is arepetitive operation, and it is possible that the received signalstrength was previously in the range requiring disablement and was thusdisabled. Such a situation may occur if a driver exchanges seats with apassenger. While a determination can be made, it is optional, and theoperation may simply always set an enablement state.

If the determination in operation 204 is that the measured signalstrength is above SSL threshold 116, it is presumed that the user is inthe driver's area 110 and the MCD 110 next executes a speed obtainmentoperation 206 wherein the motor vehicle speed is obtained from one ofthe OBD 102 or the GPS 112 of the MCD 110. Various embodiments of thisoperation are detailed below and in FIGS. 3c -3 g.

The method next proceeds to a determination operation 208 wherein it isdetermined whether or not the motor vehicle 100 is traveling at or abovepre-determined the speed threshold 114. If the motor vehicle speed isbelow the speed threshold 114, the method proceeds to a re-enablementoperation 212 which is the same as re-enablement operation 211. Thisaddresses the situation wherein the vehicle speed was previously in therange requiring disablement and the input device 120 was thus disabled.Such a situation may occur if a driver was previously driving and hasnow pulled over and stopped the vehicle 100 or reduced the vehicle speedto a level below the speed threshold 114. While a determination can bemade as to whether disablement is in effect, it is optional, and theoperation may simply always set an enablement state.

If the determination operation 208 yields a positive result, a disableinput device operation 210 is executed wherein the application program111 sends a disablement command for the input device 120 via theoperating system of the MCD 110 to prevent operation of the input device120. Thus, the method determines that the user is in the driver'scompartment 110 and that the vehicle speed is at or above the SSLthreshold 116 to prevent operation of the input device 120.

The operations 211, 212, and 210 all are followed by a link verifyingoperation 213 to address a situation wherein a previously establishedlink has been lost. If the result is negative, the establish linkoperation is 200 is then executed to attempt to again establish a link.If the result is positive, the signal strength measuring operation 202is again executed and the method repeats to continuously monitor whetherthe MCD 110 is in the driver's area 110 and whether the vehicle speedrequires disablement. Any additional MCD that is brought into range ofthe transmission apparatus 130 is also optionally configured to executethis method.

FIG. 3b is a flowchart of the link establishing operation 200 of FIG. 3a. The procedure begins with a bond execution operation 214. Thisoperation provides hand shaking signals to establish a bond with thetransmission apparatus 130 and may make multiple attempts in an effortto establish the bond, or link. After execution, flow proceeds to a bonddetermination operation 215 wherein it is determined whether a bond hasbeen made. If the determination is positive, flow proceeds to return 216which continues flow in the flowchart of FIG. 3 a. If the determinationis negative, flow proceeds to a re-enablement operation 217 whichoperates to explain the prior re-enablement operations 211 and 212. Inthis instance, since a bond could not be established it is possible thatthe transmission apparatus 130 is not operating. This may be due anelectrical system failure in the vehicle 100 in which case it is likelythe vehicle is not operating. Following the re-enablement operation 217,a quit operation 218 is executed and the program ceases.

FIGS. 3c-3g are flowcharts of various embodiments to obtain vehiclespeed operation 206 wherein determinations are made as to whether to usethe GPS speed provided by the GPS module 112 of the MCD 110 or the speedprovided by the OBD 102. In FIG. 3c , a first embodiment of the vehiclespeed operation 206 is shown and designated 206 a. A determinationoperation 221 determines if a GPS speed can be obtained. If thedetermination is negative, such as in the event that the MCD 110 isshielded from GPS reception or the GPS is otherwise disabled, flowproceeds to an OBD speed operation 223 which obtains the OBD speedtransmitted by the transmission apparatus 130 and assigns the value tothe vehicle speed to be used in the method. If the determination ispositive, an obtain GPS speed operation 221 a is executed followed by anobtain OBD speed operation 223 a. The OBD speed is sent by thetransmission apparatus 130 as detailed below with reference to aflowchart of operation of the transmission apparatus 130. In anaveraging operation 225, an average of the GPS speed and the OBD speedis calculated and is assigned to the vehicle speed. As will be madeevident below, such averaging is not a requirement of the presentdisclosure but an optional feature which may enhance accuracy of thedetermination of vehicle speed. In either scenario flow proceeds toreturn operation 230 from which the flow of the procedure in FIG. 3acontinues.

In FIG. 3d , a second embodiment of the vehicle speed operation 206 isshown and designated 206 b. A determination operation 221 determines ifa GPS speed can be obtained. If the determination is negative, flowproceeds to an OBD speed operation 223 which obtains the OBD speedtransmitted by the transmission apparatus 130 and assigns the value tothe vehicle speed to be used in the method. If the determination ispositive, a GPS speed operation 222 is executed and the GPS speed isassigned to the vehicle speed. In either scenario flow proceeds toreturn operation 230 from which the flow of the procedure in FIG. 3acontinues.

A third embodiment of the vehicle speed operation 206 is shown in FIG.3e and designated 206 c. A determination operation 226 determines if anOBD speed can be obtained. If the determination is negative, flowproceeds to a GPS speed operation 228 which obtains the GPS speedprovided by the GPS module 112 and assigns the value to the vehiclespeed to be used in the method. If the determination is positive, an OBDspeed operation 227 is executed and the OBD speed is assigned to thevehicle speed. In either scenario flow proceeds to return operation 230from which the flow of the procedure in FIG. 3a continues.

In the above speed determining operations, when the MCD 110 is not ableto retrieve the motor vehicle speed due to loss of a GPS signalreception, unavailable GPS speed data, a faulty or missing GPS module112 the motor vehicle speed data is be obtained through the motorvehicle's OBD subsystem. The OBD subsystem 160 includes a set ofElectronic Control Units processing sensor data throughout the motorvehicle 100. FIG. 2 also illustrates a configuration with thetransmission apparatus 130 connected to OBD's Diagnostic Link Connector(DLC) 161. DLC 161 is typically located under the dashboard andconnected to Electronic Control Unit (ECU) 160. ECU 160 processesinformation from various sensors and other ECUs contained within themotor vehicle 100 and broadcasts this information as a series of OBDCodes to DLC 161. SAE J1962 specifies the location of the DLC 161 asdiscussed above. The transmission apparatus 130, connected directly toDLC 161, will be located in the nearest proximity to operator controlarea 140 resulting in a high signal level from the transmissionapparatus 130 measured at the MCD 110. The transmission apparatus 130communicates with the MCD 110 over the wireless link signal 170. In theabove embodiments, the wireless link signal 170 broadcasts the vehiclespeed of the motor vehicle 100. In an embodiment, the wireless linksignal 170 will utilize Bluetooth® Smart-compliant transceivers.

In FIG. 3f , a fourth embodiment of the vehicle speed operation 206 isshown and designated 206 d. A GPS speed is obtained in the operation228. Flow proceeds to return operation 230 from which the flow of theprocedure in FIG. 3a continues. This embodiment relies only on the GPSspeed provided by the GPS module 112 and is suitable for GPS enabledMCD's.

A fifth embodiment of the vehicle speed operation 206 is shown in FIG.3g and designated 206 e. The OBD speed operation 223 is executed and theOBD speed is assigned to the vehicle speed and flow proceeds to returnoperation 230 from which the flow of the procedure in FIG. 3a continues.This embodiment does not rely on a GPS module 112 for speed measurement.

Referring to FIG. 4, a flowchart of an embodiment of a method ofoperation of the transmission apparatus 130 is shown. The operationstarts with the power up of the transmission device. An engine runningoperation 302 queries the OBD system 160 to determine if the engine isrunning. If the determination is negative the operation then ends. Ifpositive, an OBD speed retrieval operation 304 is executed and thevehicle speed is transmitted from the OBD 160. Next a bonding operation306 is executed wherein the controller 104 operates the transceiver 105to effect bonding with the MCD 110 and other MCD's in the receptionrange. Once the bonding has been achieved, a speed transmissionoperation 308 is executed wherein the OBD speed of the vehicle 100 istransmitted to the MCD 110 and other receiving MCD's. Followingtransmission, a repeat operation is executed wherein flow is directedback to the engine running operation 302 so that further bonding andtransmission of speeds may occur. As an alternative, it may be assumedthat the engine is running and operation 302 omitted. In this case,bonding and speed transmission is continuously effected.

Referring to FIG. 5, an embodiment of the transmission apparatus 130 isshown in the form of transmission apparatus 130 a. The controller 103 isembodied as an OBD-to-RS232 interpreter 103 a connecting to DLC 161. Theinterpreter 103 a is an integrated chip such as ELM Electronics ELM327or similar. The ELM327 supports OBDII protocols including SAE J1850 PWM,SAE J1850 VPW, ISO 9141-2, ISO 14230-4 (KWP), and ISO 15765-4 (CAN). Theoutput from the interpreter 103 a interfaces with the wirelesstransceiver 105 which includes an embedded processor such as NordicnRF51822 multiprotocol single chip radio transceiver with SRM CortexCPU. The Nordic nRF51822 includes a UART digital interface forconnection to the ELM327 RS232 output interface.

It should be noted that vehicle speed data obtained through the OBDsubsystem may be contained in a Parameter ID (PID). The PID may requiretranslation to extract a numeric value of the vehicle speed. The PID maybe translated by controller 104 of the transmission apparatus 130 or PIDmay be transmitted to the MCD 110 and translated by the applicationprogram 111.

In various embodiments, both the vehicle speed from GPS 12 and vehiclespeed from the OBD subsystem may be available to the application program111 which may select one vehicle speed of the two to compare to thespeed threshold 114. As a further optional enhancement, the applicationprogram 111 may combine the two values for vehicle speed to achieve amore robust value of the motor vehicle speed.

In another embodiment of the system and method of the presentdisclosure, the application program 111 may operate using only GPS speeddata obtained via the GPS module 112. In this embodiment, as will berealized by those skilled in the art, the transmission apparatus 130need not transmit vehicle speed data hence the OBD speed retrievaloperation 304 and the OBD speed transmission operation 308 may beomitted and the transmission apparatus need only effect the bondingoperation 306 whereby the application program 111 may determine areceived signal strength. It will be further realized in light of thisdisclosure that a wireless communication may be effected that does notrequire pairing, or bonding, as in the aforesaid embodiment theapplication program 111 need only determine a signal strength withoutneed for actually exchanging data, in which case the wirelesstransceiver may be replaced with a wireless receiver.

The wireless link signal 170 may broadcast other vehicle operatingparameters available using existing and future OBD PID codes to indicatewhen the motor vehicle 100 is in operation and in motion. These includecodes for fuel consumption, fuel pressure, intake and exhaust controlsettings, throttle/pedal position, cruise control, clutch position andignition/distributor engine speed to name a few. Any of these codescould be used when determining if it is safe to enable the input device120 of the MCD 110.

It is envisioned that the user may disable or otherwise circumventapplication program 111 should the user wish to use input device 120after application program 111 disables the input device 120 in themanner discussed herein. For example, the user may wish to send a text,email, etc. after application program 111 disables the input device 120and may disable application program 111 to prevent application program111 from continuing to disable the input device 120. Alternatively,should the user know that he or she will want to use input device 120 ata time when the application program would disable input device 120, suchas, for example, at a time when the user is in the operator control area140 and the motor vehicle 100 is in motion, the user may attempt todisable application program 111 before the application program 111disables input device 120. It is further envisioned that the user mayattempt to circumvent the disablement of input device 120 by switchingto another input device, such as, for example, another keyboard. Assuch, in some embodiments, the system of the present disclosure includesfeatures to detect if a user, such as, for example, an owner or user ofMCD 110 disables or otherwise circumvents application program 111.

The MCD 110 includes a processor that runs the application program 111.In some embodiments, the processor is configured to detect if the userdisables or otherwise circumvents application program 111. It isenvisioned that the processor can detect if the user disablesapplication program 111 after the application program 111 disables inputdevice 120. That is, the processor can detect if the user disablesapplication program 111 after the measured signal strength is at orabove the SSL threshold 116 (e.g., when the MCD 110 is determined to bewithin operator control area 140) and/or when the motor vehicle 100 isin motion or it is determined that the motor vehicle 100 is traveling ata rate of speed above the speed threshold 114. As shown in FIG. 6, forexample, the processor can execute an application disablementdetermination operation 232 after the input device 120 has been disabledto determine if the application program 111 has been disabled. In someembodiments, the application disablement determination operation 232 mayinvolve determining if the application program 111 is turned off orotherwise disabled after the disable input device operation 210 isexecuted.

It is envisioned that the processor may be configured to detect if theuser disables application program 111 before application program 111disables input device 120. That is, the processor can detect if the userdisables application program 111 before the measured signal strength isat or above the SSL threshold 116 and/or the motor vehicle 100 is inmotion or it is determined that the motor vehicle 100 is traveling at arate speed that is above the speed threshold 114. In embodiments,wherein the processor may is configured to detect if the user disablesapplication program 111 before application program 111 disables inputdevice 120, application disablement determination operation 232 mayoccur at any point after the establish link operation 200 and before thedisable input device operation 210.

In the embodiments discussed above that include the applicationdisablement determination operation 232, if the processor determinesthat the application program 111 has not been disabled, the method shownin FIG. 3a and discussed herein will continue in the manner shown inFIG. 3a and discussed herein. For example, in embodiments wherein theprocessor detects that the user did not disable application program 111after the application program 111 disables input device 120, the methodwill continue to the link verifying operation 213, as shown in FIG. 6.In embodiments wherein the processor detects that the user did notdisable application program 111 before the application program 111disables input device 120 (before the disable input device operation 210is executed), the method will continue to the next operation, such as,for example, one of the operations after the establish link operation200 and before the disable input device operation 210.

Alternatively, where the processor determines that the applicationprogram 111 has been disabled, the processor will execute a log creatingoperation 234, as shown in FIG. 6, for example. In some embodiments, thelog creating operation 234 includes creating a log of dates and times inwhich the application program 111 has been disabled. In someembodiments, the log creating operation 234 includes sending the log. Insome embodiments, the log creating operation 234 includes sending analert indicating that the application program 111 has been disabledand/or sending the log. In some embodiments, the log and/or the alert issent to a previously established owner contact of the MCD 110. Thepreviously established owner contact may be an employer, for example.This allows the employer to be notified if and when the user of MCD 110disables the application program 111. This can be beneficial where theemployer is a service provider, such as, for example, a delivery serviceor a provider of services wherein employees use a vehicle provided bythe employer, and will thus allow the employer to know if the employeeis not using the application program 111. This may indicate that theuser of MCD 110 is not following a company policy of the employer, suchas, for example, a policy that requires that the application program 111be used at all times and/or when the user is driving one of theemployer's vehicles. In some embodiments, the log and/or the alert aresent to the previously established owner contact electronically viaemail or text message, for example. It is envisioned that the alertand/or the log may be sent over a secure connection.

In some embodiments, the alert and/or the log may be sent to a serverthat is owned or maintained by the provider of the application program111. In such embodiments, the alert and/or log can be viewed and/ormanaged by the provider of the application program 111 and/or a customerof the application program 111, such as, for example, an entity thatpurchases or otherwise installs the application program 111 for use inmobile computing devices, such as, for example MCD 110. For example, theprovider of application program 111 may provide a password to the entitythat purchases or otherwise installs the application program 111 so thatthe entity can log onto the provider's server to view and/or manage thelog and/or alert.

In some embodiments, the processor can be configured to detect if theuser attempts to switch to another input device, such as, for example,another keyboard, before or after application program 111 disables theinput device 120. In embodiments wherein the processor is configured todetect if the user has switched input devices before application program111 disables input device 120, the processor can execute an input deviceswitching determination operation 232 a after the input device 120 hasbeen disabled to determine if the user has switched to another inputdevice, as shown in FIG. 6a , for example. In some embodiments, theinput device switching determination operation 232 a may involvedetermining if the user has switched to another input device after thedisable input device operation 210 is executed. In embodiments, whereinthe processor is configured to detect if the user has switched inputdevices before application program 111 disables input device 120, inputdevice switching determination operation 232 a may occur at any pointafter the establish link operation 200 and before the disable inputdevice operation 210.

In the embodiments discussed above that include the input deviceswitching determination operation 232 a, if the processor determinesthat the input device has been switched to an input device that is notinput device 120, the method shown in FIG. 3a and discussed herein willcontinue in the manner shown in FIG. 3a and discussed herein. Forexample, in embodiments wherein the processor determines that the userdid not switch to another input device after the application program 111disables input device 120, the method will continue to the linkverifying operation 213, as shown in FIG. 6 a. In embodiments whereinthe processor determines that the user did not switch to another inputdevice before the application program 111 disables input device 120, themethod will continue to the next operation, such as, for example, one ofthe operations after the establish link operation 200 and before thedisable input device operation 210.

Alternatively, where the processor determines that the user switched toanother input device, the processor will execute a log creatingoperation 234 a, as shown in FIG. 6a , for example. In some embodiments,the log creating operation 234 a is similar to log creating operation234 discussed above and will create a log and/or alert indicating thatthe user of MCD 110 switched to another input device. As with logcreating operation 234, log creating operation 234 a may include sendingthe log and/or alert to a previously established owner contact and/or toa server that is owned or maintained by the provider of the applicationprogram 111.

It is envisioned that it may be beneficial to establish where and wheninput device 120 is disabled. As such, in some embodiments, the systemof the present disclosure includes features to record data, such as, forexample, data concerning why input device 120 was disabled by theapplication program 111 and the time and place in which input device 120was disabled by the application program 111. The recorded data maycoincide with other data recorded by the OBD 160, for example. Forexample, in some embodiments, the data concerning why input device 120was disabled by the application program 111 may be compared or otherwiseused in connection with “black box” accident data from the OBD 160 toestablish the state of MCD 110 at the time of an accident for thepurposes of establishing liability. For example, such data may be usedto determine if the MCD 110 was in use at the time of the accident.

In some embodiments, the processor of the MCD 110 discussed above isconfigured to record data concerning the disablement of input device 120after application program 111 disables input device in a disablementdata recording operation 236, as shown in FIG. 7. In some embodiments,the disablement data obtained in the disablement data recordingoperation 236 includes recording a vehicle parameter, such as, forexample, the speed of the vehicle 100, that caused (or contributed tocause) the application program 111 to disable input device 120. In someembodiments, the speed that is recorded in the disablement datarecording operation 236 is the speed obtained during speed obtainmentoperation 206. In some embodiments, the disablement data discussedherein is obtained by pairing the processor of MCD 110 and/or theapplication program 111 to OBD 160 such that the processor of MCD 110and/or the application program 111 are in communication with OBD 160 toallow the processor of MCD 110 and/or the application program 111 tocommunicate with OBD 160 so as to obtain information from OBD 160.

In some embodiments, the disablement data includes other data, in placeof, or in addition to, the speed of vehicle 100. For example, thedisablement data may include engine status of vehicle 100, such as, forexample, data indicating if the engine is running or not at the timeinput device 120 is disabled by application program 111. In someembodiments, the processor obtains the engine status data in thedisablement data recording operation 236 by communicating with the OBD160, as discussed herein. In some embodiments, the disablement data mayalso include the GPS location of vehicle 100 and/or MCD 110 at the timeinput device 120 is disabled by application program 111. The GPSlocation of vehicle 100 may be obtained in the disablement datarecording operation 236 by communicating with the OBD 160 bycommunicating with the OBD 160, which, in some embodiments, may includea GPS module. The GPS location of MCD 110 may be obtained in thedisablement data recording operation 236 by communicating with GPSmodule 112 of MCD 110. In some embodiments, the disablement data mayalso include input device status at the time input device 120 isdisabled by application program 111. The input device status may includedata indicating whether input device 120 is enabled or not (e.g.,whether or not input device 120 has been disabled by the applicationprogram 111). The input device status may be obtained in the disablementdata recording operation 236 by communicating with the processor of MCD110.

The processor may execute a log creating operation 238 using thedisablement data obtained in the disablement data recording operation236 to create a log that establishes where the input device 120 is whenthe input device 120 is disabled by the application program 111 and/orthe specific time when the input device 120 is disabled by theapplication program 111. That is, in addition to the disablement datadiscussed herein, the log may include dates and times when the inputdevice 120 is disabled by the application program to show engine status,speed of travel and/or GPS location each time input device 120 isdisabled by the application program 111.

In some embodiments, the processor will execute a log sending operation240 to send the log created in log creating operation 238. In someembodiments, the log sending operation 240 includes sending an alertindicating that the input device 120 has been disabled and/or the logcreated in log creating operation 238. In some embodiments, the logand/or the alert is sent to a previously established owner contact ofthe MCD 110. This allows the previously established owner contact to benotified if and when the input device 120 is disabled by applicationprogram 111, where vehicle 100 and/or MCD 110 is when input device 120is disabled by application program 111 and the reasons why applicationprogram 111 disabled input device 120. In some embodiments, the logand/or the alert is sent to the previously established owner contactelectronically via email or text message, for example.

In some embodiments, the processor of MCD 110 executes a log correlationoperation 242, as shown in FIG. 7 a. The log correlation operation 242correlates the log created in log creating operation 238 with other dataor records. For example, in some embodiments, the log correlationoperation 242 correlates the disablement data discussed above with datarecorded and/or stored by OBD 160, such as, for example, “black box”accident data. That is, the log correlation operation 242 will combinethe “black box” accident data with the disablement data to provide thedata in one place so that the log can quickly establish the state of MCD110 at the time of an accident, for example. This may be beneficial indetermining whether the user of MCD 110 was using MCD 110 at the time anaccident occurred, which can help in determining whether the user of MCD110 was responsible for the accident (e.g., whether the user caused theaccident). These factors can be important in determining liability.

The processor may then execute a log sending operation 244 to send thedata from the log correlation operation 242 to a previously establishedowner contact of the MCD 110. In some embodiments, the data is sent tothe previously established owner contact electronically via email ortext message, for example. In some embodiments, the previouslyestablished owner contact is an insurance company that can use the datato determine the user of MCD 110's liability, if any, which may affectthe insurance company's responsibilities in connection with accident inreimbursing the user of the MCD 110 and/or another party for damageand/or injuries incurred as a result of the accident. The previouslyestablished owner contact may also be an employer, such as, for example,a delivery service or a provider of services wherein employees use avehicle provided by the employer, and will thus allow the employer todetermine if the user of the MCD 110 was responsible for causing theaccident and/or if the user of the MCD 110 violated certain companypolicies, such as, for example, a policy to not use a mobile computingdevice while driving.

As with the data regarding the disablement of the program application111, the log sent by log sending operation 240 and/or log sendingoperation 244 may be sent to a server that is owned or maintained by theprovider of the application program 111. In such embodiments, the logcan be viewed and/or managed by the provider of the application program111 and/or a customer of the application program 111, such as, forexample, an entity that purchases or otherwise installs the applicationprogram 111 for use in mobile computing devices, such as, for exampleMCD 110. For example, the provider of application program 111 mayprovide a password to the entity that purchases or otherwise installsthe application program 111 so that the entity can log onto theprovider's server to view and/or manage the log.

In some embodiments, the log sent by log sending operation 240 and/orlog sending operation 244 may be managed by an end user, such as, forexample, the user of MCD 110 and/or by the previously established ownercontact of the MCD 110 to whom the log was sent to during log sendingoperation 240 and/or log sending operation 244. In some embodiments, thelog may only be viewed or deleted, but cannot be modified, in order tomaintain the integrity of the data. This may be beneficial to using thedata provided in the log in determining liability for insurance, asdiscussed herein, or any of the other purposes discussed herein.

The foregoing disclosure of the exemplary embodiments of the presentinvention has been presented for purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Many variations andmodifications of the embodiments described herein will be apparent toone of ordinary skill in the art in light of the above disclosure. Thescope of the invention is to be defined only by the claims appendedhereto, and by their equivalents.

Further, in describing representative embodiments of the presentinvention, the specification may have presented the method and/orprocess of the present invention as a particular sequence of steps.However, to the extent that the method or process does not rely on theparticular order of steps set forth herein, the method or process shouldnot be limited to the particular sequence of steps described. As one ofordinary skill in the art would appreciate, other sequences of steps maybe possible. Therefore, the particular order of the steps set forth inthe specification should not be construed as limitations on the claims.In addition, the claims directed to the method and/or process of thepresent invention should not be limited to the performance of theirsteps in the order written, as one skilled in the art can readilyappreciate that the sequences may be varied and still remain within thespirit and scope of the present invention limited to the particularsequence of steps described. As one of ordinary skill in the art wouldappreciate, other sequences of steps may be possible. Therefore, theparticular order of the steps set forth in the specification should notbe construed as limitations on the claims. In addition, the claimsdirected to the method and/or process of the present invention shouldnot be limited to the performance of their steps in the order written,as one skilled in the art can readily appreciate that the sequences maybe varied and still remain within the spirit and scope of the presentinvention.

It will be apparent to those skilled in the art that variousmodifications and variations can be made to various embodimentsdescribed herein without departing from the spirit or scope of theteachings herein. Thus, it is intended that various embodiments coverother modifications and variations of various embodiments within thescope of the present teachings.

1-20. (canceled)
 21. A wireless transmission system comprising: a transmission apparatus that transmits a wireless signal indicative of a vehicle parameter; and a telephone having an input device for accepting user input and a wireless transceiver configured to receive the wireless signal, the telephone including a processor that communicates with the wireless transceiver and the input device, the processor being configured to run an application that disables the input device if the vehicle parameter exceeds a threshold, the processor being further configured to detect if the application is disabled.
 22. A wireless transmission system as recited in claim 21, wherein the telephone is a smart phone.
 23. A wireless transmission system as recited in claim 21, wherein the processor creates a log of each time the application is disabled.
 24. A wireless transmission system as recited in claim 21, wherein the processor sends an alert if the application is disabled.
 25. A wireless transmission system as recited in claim 24, wherein the alert is sent to a previously established owner contact.
 26. A wireless transmission system as recited in claim 24, wherein the alert is sent to a third party.
 27. A wireless transmission system as recited in claim 26, wherein the third party is an insurance company.
 28. A wireless transmission system as recited in claim 26, wherein the third party is an entity responsible for managing a number of vehicles and drivers.
 29. A wireless transmission system comprising: a transmission apparatus that transmits a wireless signal indicative of a vehicle parameter; and a telephone having an input device for accepting user input and a wireless transceiver configured to receive the wireless signal, the telephone including a processor that communicates with the wireless transceiver and the input device, the processor running an application that disables the input device if the vehicle parameter exceeds a threshold, the processor creating a log that includes the vehicle parameter when the input device is disabled.
 30. A wireless transmission system as recited in claim 29, wherein the vehicle parameter is speed of the vehicle.
 31. A wireless transmission system as recited in claim 29, wherein the transmission apparatus is in communication with an on board diagnostic system of a vehicle, the on board diagnostic system being configured to detect the vehicle's GPS location, the log including the vehicle's GPS location when the input device is disabled.
 32. A wireless transmission system as recited in claim 29, wherein the processor is configured to detect the telephone's GPS location, the log including the telephone's GPS location when the input device is disabled.
 33. A wireless transmission system as recited in claim 29, wherein the log includes dates and times when the input device is disabled.
 34. A wireless transmission system as recited in claim 29, wherein the transmission apparatus is in communication with an on board diagnostic system of a vehicle, the on board diagnostic system being configured to store accident data that is included in the log.
 35. A wireless transmission system as recited in claim 34, wherein the processor compares the accident data with dates and times when the input device is disabled.
 36. A method comprising: transmitting a wireless signal indicative of a vehicle parameter to a telephone device having an input device for accepting user input and a wireless transceiver configured to receive the wireless signal; running an application using a processor of the telephone; disabling the input device using the application if the vehicle parameter exceeds a threshold; and creating a log using the application, the log including vehicle data at a time when the input device is disabled.
 37. A method as recited in claim 36, wherein the log includes dates and times when the input device is disabled.
 38. A method as recited in claim 36, further comprising pairing the application to an on board diagnostic system of a vehicle, the on board diagnostic system being configured to detect the vehicle data.
 39. A method as recited in claim 38, wherein the vehicle data includes at least one of engine status, speed of travel and location.
 40. A method as recited in claim 38, wherein the on board diagnostic system is configured to record accident data, the log including the accident data. 